Read CI at the job level, not the run level - #569
Merged
Conversation
Reflection on #566: I read a run-level conclusion of success while the job had concluded failure, and told Paul a re-run had passed when it had not. The same session also had a monitor fire a false 'settled' because an empty check list contains no 'pending' to wait on. Both are the same mistake - trusting a summary signal over the specific one, and reading 'no data yet' as 'done'. Costly here because the screenshot job is routinely expected-red and every merge decision depends on reading it precisely. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011SP5gaqXEgUie8pdFrmbeJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reflection on #566: I read a run-level conclusion of success while the job
had concluded failure, and told Paul a re-run had passed when it had not.
The same session also had a monitor fire a false 'settled' because an empty
check list contains no 'pending' to wait on. Both are the same mistake -
trusting a summary signal over the specific one, and reading 'no data yet'
as 'done'. Costly here because the screenshot job is routinely expected-red
and every merge decision depends on reading it precisely.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_011SP5gaqXEgUie8pdFrmbeJ